Hi Robert,
To restore KFLOP to a virgin state and "start over". Flash New Version to KFLOP.
I think it is better to only compile-download the programs. They should only run when instructed to run at start up or when another runing Thread instructs them to start.
Flashing User Data is ok but unnecessary for the tests we are trying to perform. It also adds some potential for confusion by making changes compounded on top of changes. Without Flashing it is easy to start over from scratch with just a KFLOP power cycle.
Persist variable #0 is often used dynamically to pass values so it isn't surprising that it might have different values from time to time. I don't Think K2 used it for any important configuration settings.
I would do this sequence:
#1 Flash New Version to KFLOP to start over.
#2 Cycle Power on KFLOP
#3 Compile/download/run (in any Thread) the program to restore the persist variables.
#4 Compile/download code to Thread #1 and #6
#5 Now run Thread #6 (this should be the equivalent of a boot up cycle)
#6 Verify everything works exactly the same as with the original KFLOP
HTH
Regards
TK
Hi Tom,
I'm not sure what someone else might have done, it is an open machine in the shop. But this is what I did:
1. Compiled persist data and saved it as a new program.
2. removed and replace KFLOP with new one.
3. Loaded Thread #1,#6 and compiled-download-run
4. Set Thread #6 to run at startup
5. Flashed User Memory.
6. Restarted computer/cnc
Things seemed to work the same as before.
I did not do anything with the saved persist data program because it was running. Also, I had saved the persist data a week earlier and then again right before I swapped out the KFLOP and I notice that the first data line was different. So, I saved that
persist data as well just in case.
So, by your last comment should I have not Flashed User Memory? And should I have run the persist data program in Thread #7 as well because I did not do this.
Any way to start over with the new KFLOP?
Robert
Hi Robert,
If you compile/download the appropriate programs to the appropriate Threads (without Flashing) then the New KFLOP should behave exactly like the original KFLOP and you will know exactly what code is in use. Are you able to do that? If so we can then look
at the code to see why it behaves the way that it does.
HTH
Regards
TK
Good Morning Tom,
I did try all of those steps but the system would freeze every time I tried to execute a command. I did get it to work this morning though. I had saved a complete copy of the KFLOP and the 432 program files and swapped them all out for the corrupted ones.
It works like it used to now.
I still have the annoying old problem with the z-touch. If I use the z-touch command, the machine will home properly once. After that, if I use the home command it will home to the limit switches but then travel off home in either the x or y position a
few inches. Just one, not both, and there does not seem to be any pattern. Every time I home it after that it doubles the distance. Eventually it will crash the axis. To get around this problem, I will use the z-touch to get the bit length, save it, and
then shut down the computer and the cnc. When I boot back up, it will home without the glitch as long as I don't use the z-touch again. But this work-around has it's problems as you can imagine. Also, the rotational A axis does not stop after it homes.
I can stop it manually after it homes by hitting one of the rotational arrows twice.
Now that the new KFLOP is installed, would you be willing help me with this issue?
Best,
Robert
Hi Robert,
You should have Compiled and Downloaded the Programs to the Threads.
Hopefully when you power KFLOP the LEDs flash?
You might try restoring the New KFLOP back to a virgin state by performing a Flash Recovery on the KMotion.exe Config/Flash Screen.
Regards
TK
Hi Tom,
I was wondering if you could help me with rebooting some software?
I hadn't had the time to chase some of the issues from the summer so we have just been working with the bugs in the system. But last week I decided to try putting in the new KFLOP, like we had talked about, and it seemed to work the same. Which is what we
expected. I compiled Thread 1 and 6 and flashed user memory. And Set Thread 6 for startup.
However, I think someone must have tried something on the machine because nothing seems to be talking to each other now. KMotionCNC says it's disconnected and KMotion freezes up.
I could use some guidance on what to try next. Should I put the old KFLOP back in or something else.
Thanks,
Robert
